feat: add info about cookie chunking#100
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/docs/DM82HQMfG5W6Uj9uvizXUfoz91hB |
balazsorban44
left a comment
balazsorban44
left a comment
There was a problem hiding this comment.
We should also mention to allow session cookies if you are using a proxy.
| JSON Web Tokens can be used for session tokens if enabled with `session: { jwt: true }` option. JSON Web Tokens are enabled by default if you have not specified a database. | ||
|
|
||
| By default JSON Web Tokens are signed (JWS) but not encrypted (JWE), as JWT encryption adds additional overhead and comes with some caveats. You can enable encryption by setting `encryption: true`. | ||
| By default JSON Web Tokens are not signed (JWS) but are encrypted (JWE). |
There was a problem hiding this comment.
So I realize now, this could have been addressed in a separate PR fixing #87. 😅
There was a problem hiding this comment.
Looks good now, #87 concerns can be addressed in a separate PR. Let's wait with merging until nextauthjs/next-auth#3101 is merged as well. Finishing testing on that one at production at work, everything seems to be working correctly there. Will double-check on Monday.
2 participants
Changes 💡
Adds info regarding the cookie chunking PR (nextauthjs/next-auth#3101). These were the two places that seemed like obvious candidates for more info, feel free to add on to it obviously 👍
Affected issues 🎟
Fixes #99
Screenshot (If Applicable) 📷